Add automatic release workflow #40
Conversation
- Add auto-release workflow triggered after successful CI - Compare local Cargo.toml version with crates.io version - Automatically create tags and GitHub releases when version bumped - Generate changelog from conventional commits - Publish to crates.io automatically Workflow features: - Triggers on successful CI completion on main branch - Uses semver comparison to detect new versions - Checks if tag/release already exist (idempotent) - Groups commits by type (feat, fix, docs, etc.) - Generates formatted changelog with links - Creates annotated git tags - Creates GitHub releases with changelog - Publishes to crates.io with retry logic (5 attempts) Benefits: - No manual version management needed - Automatic changelog generation - Faster release cycle - Professional release notes - Idempotent (safe to re-run) Related: Closes #39
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - uses: actions/checkout@v4 | ||
| with: | ||
| fetch-depth: 0 |
There was a problem hiding this comment.
This workflow is triggered by workflow_run after the CI job succeeds, but actions/checkout@v4 is invoked without a ref and therefore checks out whatever happens to be at main when the job starts. If another commit lands on main before this job begins (for example a version bump whose CI run is still in progress or even fails), the release pipeline will tag and publish that newer code despite it never having completed CI. Fetch the github.event.workflow_run.head_sha so the release is built from the exact commit that actually passed CI.
Useful? React with 👍 / 👎.
1 participant
Closes #39
Changes
Added automatic release workflow that triggers after successful CI completion on main branch.
Workflow Features
Version Detection:
Idempotent Checks:
Changelog Generation:
Automated Steps:
Error Handling:
Benefits
How to Use
Testing
Similar Implementation
Based on masterror auto-release workflow: https://github.com/RAprogramm/masterror/.github/workflows/auto-release.yml